Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/components/mui/editable-table/mui-table-editable.js`:
- Line 322: The EllipsisTooltip title currently uses String(row[col.columnKey]
?? "") which yields unhelpful results for objects/arrays; update the cell
rendering around EllipsisTooltip (where title is set) to use a safe formatter
(e.g., a small helper function like formatTooltipValue or reuse the base-table
formatter) that: checks for null/undefined, returns primitives via String(...),
and for objects/arrays attempts JSON.stringify with a try/catch (falling back to
Object.prototype.toString or an empty string) so the tooltip shows useful text
for complex values; update the title prop to call that formatter instead of
String(row[col.columnKey]).
- Around line 321-324: The tooltip currently always uses raw data
(String(row[col.columnKey])) while the cell shows col.render(row), causing a
mismatch; update the EllipsisTooltip title to mirror the rendered cell by using
col.render(row) when col.render is present (and falling back to
String(row[col.columnKey] ?? "") otherwise), converting any React node to text
the same way the base table fix does (e.g., via the existing helper or
ReactDOMServer.renderToStaticMarkup) so the tooltip content matches the
displayed cell; change the usage around EllipsisTooltip/title near col.render
and row[col.columnKey].

In `@src/components/mui/sortable-table/mui-table-sortable.js`:
- Line 223: The EllipsisTooltip title currently uses String(row[col.columnKey]
?? "") which yields unhelpful "[object Object]" for non-primitive values; update
the tooltip value handling in the component that renders EllipsisTooltip (look
for the JSX containing EllipsisTooltip and the variables row and col.columnKey)
to guard against objects by converting primitives with String(...) but for
objects/arrays attempt a safe JSON.stringify (with a try/catch and a fallback
like "(object)") so the title shows meaningful text for non-string values;
optionally extract this logic to a small helper (e.g., toSafeTitle(value)) and
use that when passing title to EllipsisTooltip.
- Around line 222-228: The tooltip currently uses the raw row[col.columnKey]
value instead of the rendered cell content; change the render so the
EllipsisTooltip title uses the same displayed value as the cell by computing a
displayedValue = col.render?.(row) || row[col.columnKey] (or similar) and then
pass title={String(displayedValue ?? "")} to EllipsisTooltip; update the code
paths that render the cell (the branch with EllipsisTooltip and the non-ellipsis
branch) to use this displayedValue so the tooltip matches the rendered output
(refer to col.render, row, columnKey, and EllipsisTooltip in
mui-table-sortable.js).

In `@src/components/mui/table/mui-table.js`:
- Line 172: The tooltip is using raw row[col.columnKey] instead of the displayed
rendered cell; update the EllipsisTooltip usage in mui-table.js to prefer a
column-provided tooltip string (e.g., col.tooltipContent?.(row) or
col.tooltipContent) and otherwise derive text from the rendered cell by calling
col.render(row) and converting the resulting React node to plain text
(strip/serialize children or use a small helper like renderToString/flattenText)
so the tooltip matches the visible cell; ensure you reference EllipsisTooltip,
col.render, col.tooltipContent and row when implementing the fallback.
- Line 172: The tooltip title currently uses String(row[col.columnKey] ?? "")
which yields "[object Object]" for objects/arrays; update the EllipsisTooltip
title logic (in the component rendering the table row/col — locate
EllipsisTooltip usage with row and col.columnKey) to first inspect the value: if
it's string/number/boolean use String(value), if it's object/array attempt
JSON.stringify(value) inside a try/catch and fall back to a short placeholder
like "" on error/too-large result; ensure the final value passed to
EllipsisTooltip.title is always a string.
- Around line 157-179: renderCell currently passes the raw value
row[col.columnKey] into EllipsisTooltip causing mismatched tooltip vs rendered
cell when col.render transforms data; update renderCell to derive the tooltip
text from the rendered content when col.render exists (or support an explicit
col.tooltipContent function) — e.g., compute tooltipTitle = col.tooltipContent ?
col.tooltipContent(row) : (col.render ?
extractTextFromRenderedOutput(col.render(row)) : String(row[col.columnKey] ??
"")) and pass tooltipTitle to EllipsisTooltip, keeping the visible cell content
as col.render(row) or content; touch renderCell, col.render, col.ellipsis and
EllipsisTooltip usage to implement this change.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@src/components/mui/sortable-table/mui-table-sortable.js`:
- Around line 213-214: The sortable table cell rendering in the columns.map
block is using the truthiness of col.render(row) to decide the fallback, which
incorrectly overrides valid falsy render outputs. Update the rendering logic in
mui-table-sortable.js to check whether col.render exists before calling it,
matching the existing pattern used by the editable table, and only fall back to
row[col.columnKey] when no renderer is provided.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/components/mui/truncate-text.js`:
- Around line 31-33: The TruncateText component’s children prop is too
restrictive because it is typed as PropTypes.string even though table renderers
can pass React elements from col.render?.(row). Update TruncateText.propTypes so
children uses PropTypes.node, keeping the existing truncation logic in
TruncateText unchanged since it already only truncates when children is a
string. Ensure the change is made on the TruncateText propTypes definition so
non-string nodes no longer trigger console warnings.

---

Outside diff comments:
In `@src/components/mui/sortable-table/mui-table-sortable.js`:
- Line 214: The cell rendering fallback in mui-table-sortable.js uses a truthy
check, so valid rendered values like 0, false, or empty strings get replaced by
raw row data. Update the cellContent assignment in the sortable table render
path to use a nullish fallback instead of a logical OR, keeping
col.render?.(row) when it returns any defined value and only falling back to
row[col.columnKey] when it is null or undefined.

In `@src/components/mui/table/mui-table.js`:
- Around line 158-164: The boolean short-circuit in MUITable’s cell rendering is
bypassing any custom column renderer, so boolean-backed columns can no longer
use their own labels/chips. Update the rendering flow in MUITable so col.render
is checked and used before the default boolean icon mapping, and only fall back
to CheckIcon/CloseIcon when no custom renderer is provided. Preserve the
existing boolean default behavior for columns that do not define a renderer.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/components/mui/table/utils.js`:
- Around line 7-18: The renderCell helper now returns col.render(row)
immediately, which skips the truncateText behavior for columns that define both
render and truncateText. Update renderCell to preserve the original priority
order by checking isBoolean first, then applying col.render output through the
truncateText wrapper when col.truncateText is set, and only otherwise returning
the raw rendered value.

---

Nitpick comments:
In `@src/components/mui/table/mui-table.js`:
- Line 120: The text wrapping in the table cell styles uses wordBreak in the MUI
table component, which can split normal words mid-character; update the shared
cell styling in mui-table.js to use a gentler wrapping approach like break-word
or overflow-wrap:anywhere instead, and make sure the change applies consistently
to the editable and sortable variants that reuse the same style.